EffectiveCode Review Practices

Resources

Tips & Tricks

Anti-Patterns

…provide some context behind the recommendation:

"Since this component doesn’t have any lifecycle methods or state, it could be made a stateless functional component. This will improve performance and readability. Here is some documentation."

Asking such questions implies that a perceived simple solution should have been obvious. It also forces developers to have to defend themselves. Oftentimes, these judgmental questions are just veiled demands. Instead, provide a recommendation (with documentation and citations) and leave out harsh words.

You can do _, which has the benefit of __.

Notes

Tags #above the code